Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@src/backend_task/wallet/fund_platform_address_from_wallet_utxos.rs`:
- Around line 82-86: Replace the panic-prone call to
transactions_waiting_for_finality.lock().unwrap() with fallible error
propagation consistent with other modules: acquire the mutex with
transactions_waiting_for_finality.lock().map_err(|e| e.to_string())? and then
perform proofs.insert(tx_id, None); so the function (the block in
fund_platform_address_from_wallet_utxos where the "Step 2" registration occurs)
returns an Err instead of panicking when the lock is poisoned, matching the
pattern used in create_asset_lock.rs.
- Around line 109-118: The cleanup path after broadcast_raw_transaction
currently uses transactions_waiting_for_finality.try_lock(), which can fail
transiently and skip removing tx_id; change it to acquire the mutex with
transactions_waiting_for_finality.lock().await (or blocking lock() as used in
create_asset_lock.rs) so the code waits for the lock and reliably removes the
entry, then proceed to call
db.delete_asset_lock_transaction(tx_id.as_byte_array()) and return the error as
before; ensure you reference the same mutex (transactions_waiting_for_finality)
and tx_id removal logic to mirror the safe cleanup in create_asset_lock.rs.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/ui/wallets/wallets_screen/mod.rs`:
- Around line 179-184: The current chain that builds platform_sync_info
(starting from selected_wallet.as_ref().and_then(|w| w.read().ok().map(|g|
g.seed_hash())).and_then(|hash|
app_context.db.get_platform_sync_info(&hash).ok()).map(|(ts, checkpoint,
_terminal)| (ts, checkpoint)).filter(|(ts, _)| *ts > 0)) throws away valid
cached checkpoint data when ts == 0; remove or change the final .filter(|(ts,
_)| *ts > 0) so that platform_sync_info preserves the (ts, checkpoint) tuple
even if ts == 0 (or replace the filter with a check that only discards when both
ts == 0 and checkpoint indicates no data), and update any downstream handling
(e.g., code that renders "Addresses: never synced") to consider checkpoint
presence rather than assuming ts > 0 is required for valid sync info; locate
this logic around selected_wallet, platform_sync_info, seed_hash and
app_context.db.get_platform_sync_info to apply the change.
- Around line 120-121: The platform_sync_info cache is only updated in
select_hd_wallet, causing stale sync state when selected_wallet is reassigned
elsewhere (e.g., post-removal or fallback reselection paths); add a single
helper (e.g., refresh_platform_sync_info or set_selected_wallet) that both
assigns selected_wallet and updates platform_sync_info (using the same logic as
in select_hd_wallet) and replace all direct assignments to selected_wallet
across code paths with calls to this helper so the sync panel always reflects
the newly selected wallet.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/ai-design/2026-02-24-sync-status-panel/manual-test-scenarios.md`:
- Around line 121-122: Update the described SPV expected outputs to match the
new phase-summary formatter: replace occurrences of the old "Core: Syncing --
Headers NN%" pattern with the new format that shows "current / target (pct%)"
(e.g., "Core: Syncing -- Headers 1234 / 5678 (21%)"), and add coverage for the
new "Masternodes" phase where applicable; update the related entries that still
assume only "NN%" (including the other noted occurrences of the same text) so
all examples and test scenarios show the full "current / target (pct%)" form and
include Masternodes phase output where the app now reports it.

In `@src/backend_task/core/create_asset_lock.rs`:
- Around line 53-57: The new tracing::warn! calls are not rustfmt-compliant;
locate the two uses of tracing::warn! around the
transactions_waiting_for_finality.lock() error paths (the ones that warn "Failed
to clean up finality tracking for tx {tx_id}: Mutex poisoned") and reformat the
macro invocation so the string and arguments are wrapped across lines per
rustfmt (e.g., put the format string on its own line and the variables/arguments
on following indented lines or use a single formatted string via format! before
calling tracing::warn!). Ensure both occurrences use identical, rustfmt-friendly
wrapping and compile without changing the logged message or surrounding logic.

---

Outside diff comments:
In `@src/context/connection_status.rs`:
- Around line 333-347: The comment above the refresh-throttle logic is
inaccurate; update the comment to reflect the actual timeout behavior used by
the code in the block that reads self.last_update, calls Instant::now(), checks
self.spv_status() == SpvStatus::Stopping and self.overall_state() ==
OverallConnectionState::Synced, and sets timeout to Duration::from_millis(200)
for stopping, REFRESH_CONNECTED (4s) when synced, and REFRESH_DISCONNECTED (1s)
otherwise; ensure the comment references these three concrete durations and the
conditions (SpvStatus::Stopping, OverallConnectionState::Synced) so it stays
correct.

In `@src/ui/wallets/wallets_screen/mod.rs`:
- Around line 2140-2156: The PlatformAddressBalances branch updates the selected
wallet but always calls self.refresh_platform_sync_info_cache(&seed_hash) even
if the result no longer corresponds to the currently selected wallet; modify the
BackendTaskSuccessResult::PlatformAddressBalances handling so that after
verifying the selected wallet (the selected_wallet read lock and
wallet.seed_hash() == seed_hash) and updating balances via
wallet.set_platform_address_info(...) you only call
self.refresh_platform_sync_info_cache(&seed_hash) when that same selected wallet
check succeeded (i.e., wrap the refresh call inside the same if-let guard or
re-check selected_wallet and seed_hash before calling
refresh_platform_sync_info_cache).
- Around line 12-27: The import block in this module is misformatted; run
rustfmt (cargo fmt) to fix spacing and ordering and ensure the use statements
(e.g., CoreBackendMode, SpvStatus, Component,
ConfirmationDialog/ConfirmationStatus, add_left_panel, island_central_panel,
add_top_panel, WalletUnlockPopup/WalletUnlockResult, copy_text_to_clipboard,
DashColors, AccountCategory/AccountSummary/collect_account_summaries,
MessageType/RootScreenType/ScreenLike/ScreenType, DateTime/Utc,
spv_phase_summary, Address) are properly grouped and sorted per project style so
CI formatting checks pass.